home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Libris Britannia 4
/
science library(b).zip
/
science library(b)
/
COMMUNIC
/
3459.ZIP
/
EL-SFX.EXE
/
ELX20.DOC
< prev
next >
Wrap
Text File
|
1992-09-01
|
6KB
|
147 lines
┌──────────────────────────────────────────────────────────────────┐
┌┘ ███▄ ███▄ ELX v2.0 └┐
│ █▄▄▄ █▄▄▄ ──────── │
│ ▄▄▄█ A N D ▄▄▄█ O F T Copyright (C) 1990 - All rights reserved. │
└┐ ▀▀▀ ▀▀▀ ┌┘
└──────────────────────────────────────────────────────────────────┘
ELX is supplied for use with our EaziLink/EaziHost communications
packages and may be used with both packages to provide an error
corrected file transfer facility in either direction (ie Send or
Receive).
ELX v2 is a rewrite of the ELX v1.x drivers supplied with earlier
copies of EaziLink & EaziHost. Version 2 offers an improved display,
more information on-screen and increased functionality over ELX v1.
Version 2 is fully command line compatible with the earlier ELX v1.x
drivers so it is only neccessary to replace the old .EXE file with the
new v2 .EXE file to be up and running at the simplest level. If you
wish to make use of the new 1K variant you will need to make a second
entry in EAZILINK.PRO/EAZIHOST.PRO as described later.
ELX is an Xmodem implementation. Xmodem is the most basic and most
common file transfer protocol which, when installed as an EaziLink
external protocol, will enable the user to download more exotic
external protocol drivers such as DSZ (tm) which provides the much
acclaimed Zmodem protocol.
The general form of invokation is:
Send - ELX Sn filename.ext < -h -1k >
Receive - ELX Rn filename.ext < -h >
Where: n = The number of the serial port being used (1..4)
-h = Rts/Cts hardware handshaking ON. (Default is OFF)
-1k = Force 1k block send mode. (Default block is 128 bytes.)
( NOTE: The switches in brackets '< >' are optional )
In use ELX first 'negotiates' with the remote Xmodem for CRC error
correction and only if the remote protocol does not support CRC will
ELX default to Checksum error correction. ELX can therefore be used,
unaltered, with remote Xmodem protocols which support either one or
both of these correction methods.
ELX uses a block size of 128 bytes by default but will, without the
use of the -1k switch, automatically adjust itself to receive 1K blocks
from a remote service which is sending a file by means of an Xmodem-1k
protocol implementation.
To force ELX to send 1k blocks rather than the normal 128 byte blocks,
the '-1k' switch MUST be used and the receiving Xmodem must, as ELX
does, recognise and accept 1K blocks.
For use with EaziLink/EaziHost, typical EAZILINK.PRO/EAZIHOST.PRO
entries would be as follows:
/ ELXmodem
/ --------
name ELXmodem
hotkey E
upload ELX.EXE S%port %file
download ELX.EXE R%port %file
/ ELXmodem-1k
/ -----------
name ELXmodem-1k
hotkey 1
upload ELX.EXE S%port %file -1k
download ELX.EXE R%port %file
The Screen Display
------------------
The screen displayed during a transfer looks like this:
+----------------------|ELX v2.0|------------------------+
| |
| Receiving <a> [ESC]=ABORT |
| |
| Block Size: <b> Checking: <c> Rts/Cts: <d> |
| |
| Block Number: <e> Bytes: <f> Errors: <g> |
| |
| Last Message: <h> Cps: <i> |
| |
+--------------------------------------------------------+
Where: <a> = The short name of the file being sent/received.
<b> = The transfer block size being used (128 bytes/1K).
<c> = Error checking used (CRC or Checksum).
<d> = Hardware handshake being used ('Y'es/'N'o).
<e> = Current block number being processed (1..255 cycle).
<f> = Total bytes transferred so far.
<g> = Total errors recorded so far. (Errors are corrected)
<h> = Last message generated by ELX.
<i> = Character/second transfer rate being achieved.
Notes
-----
- ELX monitors the carrier signal and will abort automatically if the
carrier is lost during file transfer.
- File transfer can be aborted by the user at any time by pressing
the [ESC] key. Depending on whether ELX is aborted in this way
at the sending or receiving end, the termination will be either
immediate or may take a minute or so for the other end to time-out.
- ELX will ALWAYS overwrite a file of the same name as that being
received. If a transfer is aborted, the partial file which has
been transferred is erased at the receiving end.
- Once ELX is invoked in receive mode, it will try to communicate
with the sender for a maximum of 40 seconds. If no link has been
established within this period of time, the receiving ELX will
assume that the sender has not been invoked and will abort.
- If your software is transmitting data at a higher rate, to the DTE,
than your modem is transmitting to the remote site over the line,
use the '-h' switch to prevent modem buffer overflow.
- ELX has not been designed as a stand alone protocol. It expects the
comms port to have been set up by the main communications package
which should then run ELX as a child process or from a DOS shell.
ELX has been designed for use with EaziLink and we do not guarantee
that it will work with other communications packages although, in
most cases, it should.
Release History
---------------
Nov 1990 - First release of ELX version 2
< P.M. Opacic, SandSoft, 5 Lytham Close, Skipton, N. Yorks. BD23 2LF >